After setting up a slave server, you can do simple tests to verify the function.

In this animated GIF, I have two applications running a UI that has PeriodicAction that does a simple update of an attribute - then a refresh and a save.

I also run the prototyper as a 3:th app against the Slave server.

Notice that the lower of the 3 is a bit choppier when getting data refresh because the first two rows are updated in the Master DB.

This is because of the transport via the MDrivenServerSynk.

This is the expected behavior of a Slave server.

The PeriodicAction looks like this:

vCurrent_Details.Company.Name:=vCurrent_Details.Company.Name+'x'; 
if vCurrent_Details.Company.Name->length>10 then  
  vCurrent_Details.Company.Name:='C' 
else  
  '' 
endif; 
selfVM.Refresh; 
selfVM.Save